Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2e name space admin features cdap #5

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

rahuldash171
Copy link
Collaborator

E2e name space admin features cdap

gcpDataProc=provisioner-gcp-dataproc
remoteHadoopProvisioner=provisioner-remote-hadoop
Create=profile-create-btn
Finish=wizard-finish-btn
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use key with starting word small? like create, finish, next, previous

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes for NameSpace admin only keyValue key is used as of now , will have to change in surya's commit as most of this attributes are used for SysAdmin.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done .

Feature: NameSpaceAdmin - Validate system admin page flow

@Namespaceadmin
Scenario:Validate user is able to create new namespace preferences inside namespace admin
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How are we validating the preferences we set ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we are adding only the design time scenarios we will be adding the validation steps when the requirement for creation with end to end tests is planned . The scope was to create sanity test suite to start with these features . We are in connect with google team to define the future scope which will be added as end to end scenarios in this month .
As of now the plan was to create the feature and to check if the tests are passing when the integration is done with e2e FW .

Then Set system preferences with key: "keyValue" and value: "systemPreferences1"
Then Click on the Save & Close preferences button


Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove extra line

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants